…ook (#2005)

The Field Zoo declared all 48 field types but shipped NO seed data, so no
field type was ever exercised with a real value — which is exactly why the
array-serialization and Field.time bugs (fixed in #2004) went unnoticed.

- Seed two field-zoo specimens ("Full" + "Minimal") covering every input-able
  field type with real values: arrays (multiselect/checkboxes/tags/repeater/
  vector), objects (composite/address/location/json/record), time (14:30 /
  09:05:30), relational (lookup→Account, master_detail→Project by externalId),
  and computed (formula=315, autonumber). `f_secret` is intentionally omitted —
  the seed path has no CryptoProvider so a secret value is refused fail-closed.
  This doubles as a runtime regression guard: a field type that can't persist
  now fails the boot seed instead of shipping silently.
- Guard the showcase_warn_over_budget hook condition with has() — a partial
  rollup update (task_count recompute) fires afterUpdate with a record lacking
  spent/budget, and CEL throws "No such key" on a bare record.spent. has() is
  the missing-key-safe macro; the noisy warning is gone.

Verified live: both specimens seed (37 populated f_* fields on Full); coverage
test 20 green; warn_over_budget "No such key" warnings = 0 after a task update.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…thoring) (#2022)

Extends the dogfood gate from "pin one example app" toward the platform's real
risk: third parties have an AI author arbitrary metadata, so every authorable
primitive needs a runtime proof — not a static shape check.

`showcase_field_zoo` carries one field of (almost) every protocol FieldType but
was only static-checked (the bundle registers it). This adds the first
capability-matrix block: write one record covering many field types over the
real REST data API, read it back, assert each round-trips with type fidelity.

- Headliner coverage = the #2004 regressions: array-typed fields
  (multiselect/checkboxes/tags) and Field.time (time-of-day) — all proven to
  round-trip end-to-end on the in-memory (WASM) driver path `objectstack dev`
  uses for :memory:.
- On first run it surfaced three real type-fidelity gaps — rating/slider/toggle
  persist but read back as strings ('4'/'25'/'1') while number/currency/percent/
  boolean round-trip correctly. They are quarantined with `it.fails` (passes
  while broken, turns RED when fixed) rather than hidden by coercion, and filed
  as a separate task.

Private package — no changeset. 21 passed + 3 expected-fail.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

fix(console): route org-less users into guided org creation on multi-org (#2004)

objectui@9130b33ec35ac79bcd0da2618be4806e49ac2475

…ad (SQLite) (#2347)

Field.time is a tz-naive time-of-day, not an instant (#2004). A
defaultValue:'NOW()' time column historically took the full SQLite
CURRENT_TIMESTAMP default, so a defaulted/legacy row read back a full
'YYYY-MM-DD HH:MM:SS' timestamp instead of a time-of-day.

formatOutput now repairs a Field.time value to just its time portion (toTimeOnly):
a legacy full timestamp (or a full ISO value that leaked into the column) is
sliced to HH:MM[:SS[.fff]], while a value already stored as a bare time-of-day is
left untouched. Deliberately NARROW + read-only (no write/filter counterpart) so
it introduces no write/read asymmetry and preserves exact round-trips for bare
time-of-day values (the field-zoo f_time guard). Runs for every dialect (a native
TIME column already returns a time-of-day → no-op). Adds a timeFields registry +
registration mirroring dateFields/datetimeFields.

Completes the temporal read normalization alongside #2346: datetime -> ISO-8601-Z,
date -> YYYY-MM-DD, time -> wall-clock time-of-day.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>